-
Notifications
You must be signed in to change notification settings - Fork 704
Add SIGNER_APPROVAL_THRESHOLD env var for lowering threshold on testnet #6375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SIGNER_APPROVAL_THRESHOLD env var for lowering threshold on testnet #6375
Conversation
Signed-off-by: Jacinta Ferrant <[email protected]>
testing a 3 miner/signer network with this env var set panics (see below).
|
i'm not sure here why |
… into feat/signer-approval-threshold-option
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
Was an accidental != vs == I think. Hopefully that is the only spot. Give it a go now and let me know how it goes :D |
Closing. There is a means to achieve similar functionality by manipulating the stacking scripts directly (enables killing of a signer/miner pair with a smaller weight distribution and system still continue chugging. Can always reopen if comes back up. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6375 +/- ##
===========================================
+ Coverage 75.62% 79.06% +3.43%
===========================================
Files 555 555
Lines 350915 351039 +124
===========================================
+ Hits 265365 277533 +12168
+ Misses 85550 73506 -12044
... and 237 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Closes #6368
Originally did this as two configuration options. One in signer, one in node. but it ended up touching more than 40 diff files in a very janky way. Even this change required more modifications than I would like, but I think its better.